AbstractVersion's static initializer called Configuration.setDefaults(...)
to install JsonOrgJsonProvider as the JVM-wide JsonPath default. Once that
class loaded, every other JsonPath user in the same process was forced onto
the org.json provider — which only recognises org.json.JSONObject as a map.
A consumer using JsonPath against Jackson-parsed maps (e.g. Spring's
WebGraphQlTester feeding LinkedHashMap responses to JsonPath) would then
fail with PathNotFoundException whenever validator classes happened to load
before that consumer first evaluated a path. Class-load order makes the
bug intermittent: it surfaces in some test environments but not others.

Replace the global mutation with a SchemaJsonPath facade that exposes a
single static parse(Object) returning a DocumentContext bound to a private
JsonOrg-configured Configuration. All JsonPath.parse(jsonObject) call sites
in AbstractVersion and the rule patchers now route through the facade, so
adding a new schema-patching rule cannot accidentally fall back to the
default provider.